Consumer Purge

Job type: JavaClosed A widely used object-oriented programming language that is designed for use in the distributed environment of the internet. It is the most popular programming language for Android smartphone applications

Archive: None

For more information on this job, see the Job Details in the Administration ConsoleClosed An operations web console that allows batch jobs to be scheduled, run manually and monitored. The console also provides for viewing and modification of business and user applicable system configuration.: In the console, navigate to System Maintenance > Jobs. In the Job List, click the name of job to open its Job Details screen.

Selection criteria

This job removes personal customerClosed In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. information, such as contact names or accountClosed In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices. passwords for terminated single subscriptionClosed A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription accounts only, following a Subscription Anonymity Request. The job considers only records where anonymity request status = P (Pending) on the SubscriptionAnonymityRequest table.

For eligible records, the job updates the anonymity request status to I (In Progress) and invokes the purge logic for the subscription in question. The job deletes records where possible and obfuscates data where it is not possible to delete records. Certain data cannot be deleted (for example, usageClosed The consumption of services, for example a subscriber using call minutes.) because legally there is a requirement to store this for a certain period of time or there may be database constraints, for example an address is still in use because an account has multiple subscriptions.

Once a subscription has been anonymised, the job sets the anonymity request status to either C (Complete) or E (Error) and sets the processed date time on the SubscriptionAnonymityRequest record to the current date and time.

The following table lists the records that are either deleted or obfuscated:

Data

Action

Subscription Services Deleted
Subscription Tariff History Deleted
Subscription Features Deleted
Subscription Bar History Deleted
Workflow Activity (including notes, actioned items and sales, ledger adjustments) Deleted
Contract History Deleted
Subscription Serial Numbers. including SIM data) Deleted
Communications History Deleted
Communications Settings and Preferences Deleted
Subscription Spend Cap Deleted
Customer Email Address Deleted
Direct Debit Mandates Deleted
Credit Card Information Deleted
Subscription Discounts Deleted
Subscription Purchases Deleted
Subscription Username Obfuscate*
Password Obfuscate
Agreement Expiry Date Set to the current date
Account Contact Name Obfuscate
For Attention Of Name Obfuscate
Account Password Obfuscate
Account Password Obfuscate
Account PIN Obfuscate
Delivery Address Name Obfuscate
Address Lines 1 - 3 Obfuscate
Post Code Obfuscate
Telephone Numbers x 2 Obfuscate
Fax Number Obfuscate
Date of Birth Obfuscate

*For numeric fields, the field is set to 0 (zero) or null value, for alphanumeric fields the field is obscured with asterisks (*).

Running the purge job

In the Administration Console, you can create a schedule for the purge job or run it as needed.

To run a job:

  1. Navigate to Daily Operations > Jobs.
  2. In the Job List, select the checkbox for the job that you want run.
  3. Click Run Now.